BugFix #41
Closed
BugFix #41
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The $Word.DisplayAlerts is messed up when "infection" is used. Script statically assumes that $Word.DisplayAlerts = $False is the best choice and therefore causes errors in environments where newer word is used. I have fixed this by re-checking the Word version and enabling appropriate $Word.DisplayAlertsvalue. The $Doc.Saveas causes errors on newer versions of Word. added one more [ref] to fix. However, not sure if it's compatible with all newer (greater than v12) versions. More testing is needed.
|
Thanks! Testing the patch, |
|
Ping ;] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The $Word.DisplayAlerts gets defaulted to $False in "infection" phase. That's not valid for newer version of MS Word. I applied (reused code form the beginning of the script) additional check so that it does not throw errors for newer versions of MS Word.
Additionally, some errors where thrown due to missing [ref] while the infected file is being saved in environments with newer MS Word versions. However, this should be further tested in order to verify if it does not require specific checks of MS Word version.